home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr49
/
tranx0d.zip
/
TRANX0D.ME
< prev
Wrap
Text File
|
1995-02-22
|
2KB
|
59 lines
TranX 0.D 2/22/95
TranX can now support Trx#: updates for The Box point mailer.
TranX has a number of new command line parameters to control how
much it will be allowed to update your system clock. This will
compliment the global /m<val> control.
examples:
TranX Ian_Smith /]300
This will prohibit TranX from updating your system clock if Ian's
clock is 300 seconds or GREATER than yours.
TranX Ian_Smith /[600
This will prohibit TranX from updating your system clock if Ian's
system clock is 600 seconds or LESS than yours.
──────────────────────────────────────────────────────────────────
You can support other tranx keywords within your log file with the
/*<TrnX_keyword> switch. Note that underscores must be used
rather than spaces.
example:
TranX Arno_Kromdijk /*_Trx#:_
This tell TranX to look for " Trx#: " rather than " Tranx: " in
the log file. I believe TranX will now work with The Box point
mailer without anything further. In other words, what you see
below is now supported providing you use the /* switch.
Trx#: 2D6C4BE5/2D6C4BA6
──────────────────────────────────────────────────────────────────
You can also define the delimeter between the system hex time
numbers in the mailer log should the need ever arise.
TranX Joe_Flabeets /@*
This will tell TranX to expect an asterisk between hex numbers
like this:
Tranx: 2D6C4BE5 * 2D6C4BA6
──────────────────────────────────────────────────────────────────
TranX now exits with an errorlevel of 8 if your system clock
has been updated. Type TranX all by itself to see the entire
list of command line switches and errorlevel exits. Error
levels that can be reported, should appear in the TranX log.
TranX now behaves properly when an update session fails. It
no longer writes to the LASTCLOK.FIL under those conditions.
eof